Commit the glossary work that we started back in March.
authorrobertl <robertl>
Tue, 3 Jul 2007 17:16:37 +0000 (17:16 +0000)
committerrobertl <robertl>
Tue, 3 Jul 2007 17:16:37 +0000 (17:16 +0000)
xmldoc/chapters/_chapters.xml
xmldoc/chapters/allchapters.xml
xmldoc/chapters/glossary.xml [new file with mode: 0644]
xmldoc/chapters/preface.xml

index c708c6b0516593f5d7b0b7562f414de72dbd6bf7..c7c29b8abf7587568c1b16fbb00015a69a82235e 100644 (file)
@@ -7,4 +7,5 @@
 <!ENTITY app_datums  SYSTEM "datums.xml">
 <!ENTITY app_garmin_icons  SYSTEM "garmin_icons.xml">
 <!ENTITY app_styles  SYSTEM "styles.xml">
+<!ENTITY app_glossary  SYSTEM "glossary.xml">
 
index 82a129bd567e878b8d52828fc04d1d04985c36b6..71400b93d9bee2490c17a85b66150bfea88e9ed8 100644 (file)
@@ -6,3 +6,4 @@
 &app_datums;
 &app_garmin_icons;
 &app_styles;
+&app_glossary;
diff --git a/xmldoc/chapters/glossary.xml b/xmldoc/chapters/glossary.xml
new file mode 100644 (file)
index 0000000..4dd7eff
--- /dev/null
@@ -0,0 +1,75 @@
+  <glossary id="Glossary">
+    <title>Glossary</title>
+    <para>Terms that are used in conjunction with GPSBabel.</para>
+    <glossdiv id="G">
+      <title>G</title>
+      <glossentry id="gl_xml">
+        <glossterm>Geocaching</glossterm>
+        <glossdef>
+          <para>GPS based "paper chase", see 
+          <ulink url="http://en.wikipedia.org/wiki/Geocaching" /></para>
+        </glossdef>
+      </glossentry>
+    </glossdiv>
+    <glossdiv>
+      <title>I</title>
+      <glossentry id="gl_itinerary">
+        <glossterm>Itinerary</glossterm>
+        <glossdef>
+          <para>same as a Route (e.g. used by TomTom)</para>
+        </glossdef>
+      </glossentry>
+    </glossdiv>
+    <glossdiv id="P">
+      <title>P</title>
+      <glossentry id="gl_poi">
+        <glossterm>Points of Interest (POI)</glossterm>
+        <glossdef>
+          <para>a collection of gas stations, post boxes, shops and
+          like.</para>
+        </glossdef>
+      </glossentry>
+    </glossdiv>
+    <glossdiv id="R">
+      <title>R</title>
+      <glossentry id="gl_route">
+        <glossterm>Route</glossterm>
+        <glossdef>
+          <para>a list of geopoints (often with names) connected in
+          a specific order. Usually a collection of geopoints
+          defining the route you want to pass while traveling,
+          created by PC software, or generated inside a GPS device.
+          They can be composed of existing waypoints, or new
+          "routepoints" might be generated.</para>
+        </glossdef>
+      </glossentry>
+    </glossdiv>
+    <glossdiv id="T">
+      <title>T</title>
+      <glossentry id="gl_track">
+        <glossterm>Track</glossterm>
+        <glossdef>
+          <para>a collection of geopoints recorded by your GPS
+          device while traveling -- "breadcrumb trails". The order
+          of trackpoints within the track is important. Usually a
+          trackpoint doesn't have a name or comment, but a
+          timestamp. This distinguishes a trackpoint from a
+          waypoint.</para>
+        </glossdef>
+      </glossentry>
+    </glossdiv>
+    <glossdiv id="W">
+      <title>W</title>
+      <glossentry id="gl_waypoint">
+        <glossterm>Waypoints</glossterm>
+        <glossdef>
+          <para>are geopoints that are not necessarily connected to
+          other points, and their order is unimportant. They can be
+          entered before, while or after you actually visit the
+          place and might have tags like name, comment and the
+          like. Usually used to mark special locations as your
+          home, a hotel or a geocache.</para>
+        </glossdef>
+      </glossentry>
+    </glossdiv>
+  </glossary>
index ab3f4fee3169546a037f12b27b8b3c6b862f9747..a839143e60dc096891e55b61ad649b5b29857e64 100644 (file)
@@ -30,7 +30,7 @@ that it was easy to add new formats and made the program freely available. <ulin
        lines of reasonable ISO C so they can be stamped
        out pretty trivially.  Formats that are ASCII text delimited in some
        fixed way can be added with no programming at all via our 
-       <link linkend ="Styles">style</link> mechanism.
+       <link linkend="Styles">style</link> mechanism.
        </para>
       </section>
    </preface>